Removing them will reduce the cost of session replication. 删除它们会减少会话复制的成本。
Currently, Community Edition implements clusters using the session replication support from either Apache Tomcat or WADI ( Web Application Distributed Infrastructure). 目前,CommunityEdition使用来自ApacheTomcat或WADI(Web应用程序分布式基础结构)的会话复制支持来实现集群。
Those services are DynaCache, memory to memory session replication, core groups, Web services caching, and stateful session bean persistence. 这些服务是DynaCache、内存到内存会话复制、核心组、Web服务缓存和有状态会话Bean持久性。
You can choose from database session persistence or memory-to-memory session replication for applications running in a cluster. 您可以为运行在集群中的应用程序选择数据库会话持久化或内存到内存的会话复制。
See Resources for a link to content that will help you configure Tomcat for failover and session replication. 参见参考资料以取得到该内容的链接,这些内容将有助于为故障转移和会话复制配置Tomcat。
The scheme provides no session failover and no session replication support. 模式没有提供会话故障转移和会话复制支持。
If a failover occurs, both the SFSB and SIP Session will failover to the single peer in its replication domain. 如果出现故障转移,SFSB与SIP会话将故障转移到其复制域中的唯一对等计算机上。
In addition, through projects such as WADI, session replication can be added to servlet containers such as Tomcat or Jetty through the servlet filtering mechanism. 此外,通过像WADI这样的项目,可以用servlet过滤机制将会话复制添加到像Tomcat或者Jetty这样的servlet容器中。
Whatever mechanism you decide on for session replication, you can improve the performance and scalability of your Web application in a few ways. 不管决定使用什么机制进行会话复制,可以用几种方式改进Web应用程序的性能和伸缩性。
This is especially crucial under failover conditions when WebSphere uses the application session ID in the encoded URI to route requests to the replication peers of the failed application servers. 这在故障转移情况下尤其重要:WebSphere使用已编码URI中的应用程序会话ID将请求路由到已失败的应用程序服务器的副本服务器。
One approach for session replication is simply to serialize the session contents and write it to a database. 一种会话复制的方法是序列化会话内容并将它写入数据库。
For containers that support minimal updating, you can reduce the cost of session replication by placing multiple, finer-grained objects in the session rather than one big monolithic object. 对于支持最小更新的容器,可以通过将多个细化的对象而不是一个大块头放到会话中而降低会话复制的成本。
Session replication enables a host of benefits& load balancing, scalability, fault tolerance, and high availability. 会话复制可以提供大量好处&负载平衡、伸缩性、容错和高可用性。
This allows to scale out application tier independent of the session replication tier. 这还可以独立于会话复制层扩展应用层。
The session replication can be configured either for full session or only modified session. 既可以针对整个会话,也可以仅针对修改的会话配置会话复制。
EJB container, Transaction service, Timer Service, Orb, Session Replication Module and other components in GlassFish application server use Shoal for accessing and interacting with cluster members. GlassFish应用服务器中的EJB容器、事务服务、定时服务、Orb、Session复制模块以及其他组件都使用了Shoal来与集群中的成员进行交互。